|
|
|
|
|
|
The Agile Image Editor was used to create this VRML 2.0 scene of Longs Peak in Rocky Mountain National Park. This example registers bands 4, 3, and 2 of a Landsat image to four 7.5 minute DEM files and a 1 degree DEM file. Click on the image to view Longs Peak in 3D if you have a VRML 2.0 plug-in such as CosmoPlayer. You can create the VRML scene yourself by installing and launching the Image Editor. |
Example VRML 2.0 Scene |
Do you ever have to assemble a number of images together to create derived images just so the derived images can be used to create more derived images, and then run out of disk space and patience? Tired of providing numeric control points to georeference an image to an elevation map, or having to run batch programs to warp images to a different projection?
Then the Agile Image Editor is for you.
The Image Editor allows you to assemble, inspect, enhance, crop, scale, project, and register images quickly and efficiently. You can then save either the resulting image or a small description file of the processing needed to recreate the image. Using the Image Editor you can edit this file, modify parameters, and add or remove operators. All the ImageVision® operators are available.
This description file is a compact representation of the final result and can be used wherever an ImageVision® image is required - as an input to ImageVision® tools and ImageVision® capable applications. Hence there is no need to store large intermediate files. The image represented by the description file may be enormous, but only the original inputs occupy significant file space and only the portions that are required to recreate the needed portion of your image are processed. It is the ability to create a description file that can be used in lieu of a standard image that makes the Image Editor unique.
When the description file is opened by any application other than the Image Editor, it appears to be a normal image, even though the operations to form the result are being performed at that time, on the fly. Notice that the file tm.agi in the description file above is actually an Image Editor description file opened as a normal image. It could also be opened by programs like imgview or imgworks.
Whenever possible, the Image Editor computes cpu-expensive information such as image statistics just once and uses the results when the image is needed. For example, a histogram equalization computes the histogram once then saves the resulting color lookup table for use when the processed image is needed.
Some images have attached information that references the image to its geographical location, like GeoTiff files or Digital Elevation Maps (DEM) from the USGS. Using visual control points you can interactively register other images to ones with geographical information; for example, you may want to place a satellite photograph on top of an image of a topographical map or a DEM. When registering the satellite image to a DEM you can view a 3D neighborhood about the current tie point as you drag the tie point. Once geographical references for images are known the images can be assembled into a mosaic (collage) and mapped in a variety of projections.
The Image Window below shows the Longs Peak image sliding across the elevation map as a tie point is being dragged. The geographic coordinates of the point as well as the pixel value are shown at the bottom of the window.
Hence you can take DEM's from the USGS, combine them into a single DEM, and project that into a Universal Transverse Mercator projection; merge three Landsat bands, enhance the result, and then create a texture mapped 3D representation for use by Open Inventor® or Performer® applications. If the terrain construction is done from ImageVision® images by the target application, no files other than the original source images and the small description files produced by the Image Editor are needed. The Image Editor can also create a tiled VRML 2.0 file of the scene.
The description file allows you to easily go back and change parameters, add or delete operators or make other changes. You don't have to remember how you did it a few months ago or what the parameters were when another change is needed.
The description files can be used as images on any supported system since the support for making them appear as ImageVision® files is freely available. The Image Editor is not required.
The Agile Image Editor requires an SGI system running at least:
Upgrades to these products are available by calling SGI at 1-(800) 800-4SGI. In addition, the latest ImageVision and Inventor EOEs are usually available on the Web at:
Licenses for the Agile Image Editor are available as Node Locked,
Floating, or short term Evaluation licenses. The "Install
License" button below will install a temporary node locked
evaluation license using the SGI license manager.
If the evaluation license has expired, you will see a diagnostic from the license manager when you launch the Image Editor. In this case, email questions@agileimage.com with your hostid to obtain a current evaluation license. Use the command 'lmhostid' in a shell window to find your hostid.
There are three images which will be installed: imageEditor, imageEditor_eoe, and imageEditor_demo.
The imageEditor is the application itself, and requires the execution support of the imageEditor_eoe product and a software license. A temporary node locked license is available as part of this installation.
The imageEditor_eoe is the Execution Only Environment. If you need to simply use a file produced by the imageEditor, then all you will need is the imageEditor_eoe product which requires no license.
The imageEditor_demo contains demonstration images. It requires the imageEditor_eoe product.
The default installation installs a N32 API version of the imageEditor and both O32 and N32 API versions of the imageEditor_eoe support. If your system configuration requires an O32 version of the editor, de-select the imageEditor.sw.base32 subsystem and select the imageEditor.sw.base subsystem instead.
The Release Notes for the imageEditor describe the necessary license and IFL configuration procedures, as well as how to get started. Help is provided through the Help menu or the "Click For Help" feature.
 |
 |
 |
| ||
For licensing or more information, mail: For the current release or information, see: |
 |
